Skip to content

Using dynamic branch name instead of hard coded ones #4788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Using dynamic branch name instead of hard coded ones #4788

wants to merge 1 commit into from

Conversation

@hector-vido
Copy link
Contributor

@hector-vido hector-vido commented Oct 23, 2025

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2025
@hector-vido hector-vido changed the title Using dynamic branch name instead of hardcoded ones Using dynamic branch name instead of hard coded ones Oct 23, 2025
@hector-vido hector-vido force-pushed the cluster-init-default-branch branch from c65276f to 8cfa867 Compare October 23, 2025 21:44
@hector-vido hector-vido force-pushed the cluster-init-default-branch branch from 8cfa867 to fbd8d61 Compare October 24, 2025 19:01
@hector-vido
Copy link
Contributor Author

hector-vido commented Oct 24, 2025

/test ci/prow/breaking-changes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@hector-vido: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test checkconfig

/test codegen

/test e2e

/test format

/test frontend-checks

/test images

/test integration

/test integration-optional-test

/test lint

/test unit

/test validate-vendor

The following commands are available to trigger optional jobs:

/test breaking-changes

/test e2e-oo

/test security

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-ci-tools-main-breaking-changes

pull-ci-openshift-ci-tools-main-checkconfig

pull-ci-openshift-ci-tools-main-codegen

pull-ci-openshift-ci-tools-main-format

pull-ci-openshift-ci-tools-main-frontend-checks

pull-ci-openshift-ci-tools-main-images

pull-ci-openshift-ci-tools-main-integration

pull-ci-openshift-ci-tools-main-lint

pull-ci-openshift-ci-tools-main-security

pull-ci-openshift-ci-tools-main-unit

pull-ci-openshift-ci-tools-main-validate-vendor

In response to this:

/test ci/prow/breaking-changes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hector-vido
Copy link
Contributor Author

hector-vido commented Oct 24, 2025

/test breaking-changes

@deepsm007
Copy link
Contributor

deepsm007 commented Oct 28, 2025

/test images

@deepsm007
Copy link
Contributor

deepsm007 commented Oct 29, 2025

/lgtm
/hold
This PR requires a quick follow-up in release repo

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 29, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 29, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 29, 2025

Scheduling required tests:
/test e2e

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test integration-optional-test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, hector-vido

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [deepsm007,hector-vido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hector-vido
Copy link
Contributor Author

hector-vido commented Nov 5, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 5, 2025

@hector-vido: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/breaking-changes fbd8d61 link false /test breaking-changes

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bear-redhat bear-redhat Awaiting requested review from bear-redhat

@pruan-rht pruan-rht Awaiting requested review from pruan-rht

Assignees

@deepsm007 deepsm007

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hector-vido @deepsm007 @openshift-ci-robot